New hygiene class surfaced by PR #31's 5-file merge-tangle.
Detector is the one-liner:

  git log --since="60 days ago" --name-only --pretty=format: \
    | grep -v '^$' | sort | uniq -c | sort -rn | head -25

No index needed — git history *is* the index. Heuristic: >20
changes / 60d on a single monolithic doc = investigate; >30 =
refactor candidate (tune after 5-10 rounds of observation).

Per-file decision is one of four:
  - refactor-split (per-row, per-round, per-section)
  - consolidate-reduce (merge with a sibling)
  - accept-as-append-only (legitimately append-only → split
    into per-round files rather than trimming)
  - observe

Empirical ranking at landing (60-day window, 2026-04-21):

   33  docs/ROUND-HISTORY.md    ← #1; merge-tangle source
   26  docs/BACKLOG.md          ← ADR already in-flight
   14  docs/VISION.md
   13  docs/CURRENT-ROUND.md
   11  docs/WINS.md
   10  docs/DEBT.md

Pair with merge-tangle fingerprints (PR #31 §9 incident log)
— a hot file is worse if also in a recent conflict list.

Triggered by Aaron 2026-04-21 ("hot file path detector
probably needs refactor if we find hot git file paths as we
just noticed, another hygene" + "detecting hot files i wonder
if you can just use git history for that and see what changes
the most"). Full reasoning + scope in
memory/feedback_hot_file_path_detector_hygiene.md
(agent-memory file, not in repo).

Scope: factory. Ships to adopters via the command-line recipe
(any repo runs the same `git log` against its own tree).

Pairs with existing rows #22 (symmetry-opportunities) and #23
(missing-hygiene-class gap-finder) — both meta-audits that
sweep for structural pressure. This row targets churn-pressure
specifically.

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

…ment-based review cadence) (#217)

Human maintainer 2026-04-23 Otto-58 named a NEW hygiene class distinct
from the ~57 mechanically-verifiable FACTORY-HYGIENE rows:

  "agents review hygene on a cadence for a specific type of thing,
   this one is look for generalization opportunities in the code,
   for example the docker for reproducability for multi agent review
   can be generalize to everyting in the project, all applieas to
   code skills docs everyting"
  "backlog"

Key insight: existing FACTORY-HYGIENE rows check "did we do X?"
(mechanical, binary). This class asks "are we applying principle P
wherever P applies?" (judgment, scope-extension). Complementary, not
duplicative.

BACKLOG row filed under new P1 section "Principle-adherence review
cadence (Otto-58 new hygiene class)". M effort.

Worked example: Docker-for-reproducibility (currently scoped to
multi-agent peer-review per Otto-55/57) generalizes to devcontainer,
per-sample Dockerfile, benchmark-harness containers, Craft module
build envs, CI image pinning. Review emits these as BACKLOG
candidates; per-candidate ROI decides which to implement.

First-pass principle catalogue (12 principles): git-native/in-repo-
first/samples-vs-production/applied-default/honest-about-error/
Codex-as-reviewer/detect-first/honor-those-before/Docker-repro/
CLI-first/trust-approval/split-attention.

Protocol shape:
  1. Define principle (1 sentence + memory citation)
  2. Current scope (1-2 concrete examples)
  3. Bounded sweep (N minutes, top-K candidates)
  4. Emit per-candidate BACKLOG rows
  5. ROUND-HISTORY row noting the review

Cadence: every 10-20 rounds per principle; sharded across agents by
principle class; first-pass triggered by principle-introduction events.

Classification (row #50): detection-only-justified — generalization
opportunities are inherently post-hoc.

Composes with row #23 (missing-class) + #22 (symmetry) + #41 (orthogonal-
axes) as judgment-based meta-audit triad/quad.

Per-user memory: project_principle_adherence_review_new_hygiene_class_
cadenced_judgment_on_generalization_opportunities_2026_04_23.md

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>